vue-a2b is about a/b testing or picking what to render and not about a/b testing && analytics. It's rather a single problem solution than suite that tries to solve couple issues simultaneously. Keeping it decoupled from analytics means smaller bundle size and complete freedom when it comes to tracking implementation

Certainly there is no conflict here with that. Just don't configure analytics.

But in most cases A/B testing means cohort analysis. That's what I'm getting at with this anyway.
It's a simple addition, and adds about 500B in weight to the package.

@softbeehive I understand that you want the package to be small and flexible. However, right now, vue-a2b is not really split testing as you say, since you are only split-serving different variants without the opportunity to actually test the impact they have.

@larsschellhas I guess you're right to expect it to be a complete solution. But it's rather a helper that solves a single problem. It's quite old and outdated by now, I wouldn't use it. @AMekss, maybe consider archiving this repo.

@softbeehive @AMekss yes, you are right! However, it was still the first option that came up in my search for an A/B- / Split-Testing solution for Vue.js.
Can you recommend another one? I'm currently using Google Optimize on other website, but I'm a bit hesitant regarding its use inside my Vue app.